Repository navigation
chore: release v0.15.1 - #708
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
这次是什么
v0.15.0 打 tag 之后合入的三条修复攒出来的补丁版:版本号
0.15.1、测试数同步、CHANGELOG 归位。顺手修的一处记账错位
#663(无会话身份的系统写入绕过写入准入)与#648(验证基线只记 HEAD)是在 v0.15.0 已经打 tag、GitHub Release 已经按 [0.15.0] 正文生成之后才合进来的,两条的 CHANGELOG 条目却落在## [0.15.0]小节内部——等于把新修复写进了一份已经发布的说明里,读 Release 的人永远看不到它们。这正是
release.yml的 verify 步骤要求「tag 版本必须在 CHANGELOG 里有同名小节」的原因,而它救不了写错小节的情况。本 PR 把这两条整段搬到## [0.15.1],与#707的图例修复合并成这一版的完整条目;[0.15.0] 恢复成发布时那一份内容。本版包含
#663系统写入(蒸馏 / dream 总览 / 目录引导)不再整片跳过写入准入的第 1 级判据#648验证基线同时记工作区脏文件清单,提交后才不会让 claim 漂移永远判不到验证
npm test:3513 tests / 3512 pass / 0 fail / 1 skippedreadme-claims/release-docs/security-doc)14/14SECURITY.md支持版本表首行已是0.15.x,无需挪格Summary by CodeRabbit